fix(wallet): fix aggressive disconnects in wallet connectivity #3807
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sdbondi
added a commit
to sdbondi/tari
that referenced
this pull request
Feb 17, 2022
* development: (28 commits) fix(wallet): fix aggressive disconnects in wallet connectivity (tari-project#3807) chore: honor decimals in ERC20 (tari-project#3809) chore: add icons to applications (tari-project#3812) fix: daily test (tari-project#3815) ci: improvements to macos pkg (tari-project#3824) ci: cargo test speedups (tari-project#3843) feat: add persistence of transaction cancellation reason to wallet db (tari-project#3842) fix: update RFC links and README (tari-project#3675) (tari-project#3839) chore: change NodeIdentity debug (tari-project#3817) fix(dan): include state_root in node hash (tari-project#3836) feat(cli): resize terminal height (tari-project#3838) feat(validator-node): initial state sync implementation (partial) (tari-project#3826) feat: update console wallet tui (tari-project#3837) feat: resize base node terminal on startup (tari-project#3827) feat(wallet): add grpc method for setting base node (tari-project#3828) chore(deps): bump follow-redirects from 1.14.5 to 1.14.8 in /applications/tari_web_extension_example (tari-project#3832) chore(deps): bump follow-redirects from 1.14.7 to 1.14.8 in /applications/tari_collectibles/web-app (tari-project#3833) chore(deps): bump follow-redirects from 1.14.5 to 1.14.8 in /applications/tari_web_extension (tari-project#3834) chore(deps): bump follow-redirects from 1.14.7 to 1.14.8 in /applications/launchpad/gui-vue (tari-project#3831) chore(deps): bump follow-redirects from 1.14.4 to 1.14.8 in /integration_tests (tari-project#3829) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
poolwhen disconnecting, so that requests for a client session will waitMotivation and Context
Observed the wallet continuously disconnecting and reconnecting to base node, resulting in many of these message:
Outbound messaging protocol failed for peer xxxxx: IO Error: 5e5731a0/4: connection is closedThis is not a confirmed fix for the issue, because it is difficult to reproduce, but I suspect the problem was not clearing the
pool in wallet connectivity when disconnecting was causing disconnect to be called whenever a peer session was requested by the monitor etc., sometimes timed in such a way that it would disconnect the new connection that was just established, and that would continue indefinitely.
How Has This Been Tested?
Manually, switching base nodes, stop base node while connected then restart